Split building-native-ui into building-native-ui + expo-router#99
Merged
Conversation
Kudo
approved these changes
Jul 5, 2026
Kudo
left a comment
Kudo
left a comment
Contributor
There was a problem hiding this comment.
thanks for the helping. good to add "using .ios.tsx / .android.tsx in src/app/ (route root) is an anti-pattern) should create platform components inside components/ but not route root.
Separate the navigation/routing half of building-native-ui into a new expo-router skill so each has a sharper trigger and an agent loads only the half it needs. - Move 6 navigation references (route-structure, tabs, toolbar-and-headers, form-sheet, search, zoom-transitions) into expo-router/references/ - Move the Routes + Navigation sections into the new expo-router SKILL.md, duplicating only a minimal shared context (Color note, @react-navigation pref, brief Expo Go note) so it stands alone - Rewrite both skill descriptions to remove scope overlap - Register expo-router in skills.sh.json, both READMEs, and eval runtime-matrix - Re-point cross-skill references (web-to-native, expo-examples) at expo-router
Ubax
force-pushed
the
split-expo-router-skill
branch
from
5a4cc62 to
5d04542
Compare
Contributor
Author
I'll create a follow-up PR for that |
jonsamp
added a commit
that referenced
this pull request
Jul 6, 2026
Prefix every skill with expo-* (framework/OSS) or eas-* (paid EAS service), and prefix each description with "Framework (OSS)." or "EAS service (paid)." so the free/paid boundary is visible in the always-loaded metadata and /expo- / /eas- discovery works. Renames to established product names: - building-native-ui (visual guide) -> expo-native-ui; navigation stays in the expo-router skill, matching the #99 split - native-data-fetching -> expo-data-fetching - use-dom -> expo-dom - web-to-native -> expo-web-to-native - add-app-clip -> expo-app-clip - upgrading-expo -> expo-upgrade - expo-observe -> eas-observe - expo-cicd-workflows -> eas-workflows - expo-deployment -> eas-app-stores (web deploy split into eas-hosting) - expo-api-routes -> eas-hosting Add CONTRIBUTING.md with documented patterns, CI checks for skill limits and plugin version bump, and bump the expo plugin to 1.7.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jonsamp
added a commit
that referenced
this pull request
Jul 7, 2026
* Organize skills with expo-* and eas-* naming Prefix every skill with expo-* (framework/OSS) or eas-* (paid EAS service), and prefix each description with "Framework (OSS)." or "EAS service (paid)." so the free/paid boundary is visible in the always-loaded metadata and /expo- / /eas- discovery works. Renames to established product names: - building-native-ui (visual guide) -> expo-native-ui; navigation stays in the expo-router skill, matching the #99 split - native-data-fetching -> expo-data-fetching - use-dom -> expo-dom - web-to-native -> expo-web-to-native - add-app-clip -> expo-app-clip - upgrading-expo -> expo-upgrade - expo-observe -> eas-observe - expo-cicd-workflows -> eas-workflows - expo-deployment -> eas-app-stores (web deploy split into eas-hosting) - expo-api-routes -> eas-hosting Add CONTRIBUTING.md with documented patterns, CI checks for skill limits and plugin version bump, and bump the expo plugin to 1.7.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Fix mangled EXPO_PUBLIC_ in expo-data-fetching quick reference --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Splits the
building-native-uiskill into two focused skills:building-native-ui(kept) — visual UI: Apple HIG styling, semantic colors, native controls, SF Symbols, media, animations, visual effects, gradients, storage, responsive layout.expo-router(new) — navigation/routing: file-based routes, Link (previews + context menus), native Stack, page titles, modals, form sheets, NativeTabs, headers/toolbars, header search bars.Changes
git mv, no rewrites) intoexpo-router/references/:route-structure,tabs,toolbar-and-headers,form-sheet,search,zoom-transitions. The 8 visual references stay inbuilding-native-ui.expo-router/SKILL.md. Duplicated only a minimal shared context (Color note,@react-navigation→expo-router/react-navigationpref) so expo-router stands alone.expo-router/agents/openai.yaml.expo-routerinskills.sh.json(App Design group), rootREADME.mdtable, pluginREADME.md, and the evalruntime-matrix.md.web-to-native,expo-examples) that referenced NativeTabs / large titles /zoom-transitions.mdfrombuilding-native-uitoexpo-router.Verification
claude plugin validate ./plugins/expo✔python3 -m json.tool skills.sh.json✔bun scripts/check-skill-limits.ts✔ (all skills within description/body limits)